Skip to content

chore(mobile): bump app version to 2.3.0 - #7914

Merged
ronishrohan merged 1 commit into
mainfrom
ao/mobile-changes/version-2-3-0
Nov 7, 2026
Merged

ronishrohan merged 1 commit into
mainfrom
ao/mobile-changes/version-2-3-0

Conversation

@Prasad-D-Ware

Copy link
Copy Markdown
Member

Code changes: +0 -0
Tests: +0 -0
Others: +1 -1

What

Bumps the mobile app version from 2.2.0 to 2.3.0 in packages/mobile/app.json, ready for the next store build. Build numbers stay with EAS (appVersionSource: "remote", autoIncrement on the production profile).

Why

2.3.0 is the first store build with the native overhaul (#7836–#7839), mobile Sentry (#7470) and the iPad hardware-Return module (#7666). None of them can ship to 2.2.0 users as an OTA, so they need a new store release.

Before / After

Before After
Settings footer and store listing version: 2.2.0 2.3.0
Runtime fingerprint on main: iOS ee5379ff…, Android f99ab5a4… iOS 52a442a3…, Android 4980814e…

The app version is part of the Expo fingerprint, so this bump also moves the runtime. That's expected for a store release: OTAs published from this tree target 2.3.0 builds only.

How

One line, as in #6602 and #7396. The 2.2.0@42 strings in lib/sentry.test.ts are test fixtures, not the app version, so they stay.

Testing

  • npx vitest run: 360 files and 3,487 tests pass.
  • npx expo-updates runtimeversion:resolve --platform ios|android on a clean tree, before and after, gives the runtimes above.
  • main at f8c84e393d, the same tree plus this one line, was tested with Release builds:
    • iOS and Android simulators;
    • a Pixel 10a (Android 17) and an iPhone 17 Pro Max (iOS 27.2) over Wi-Fi: pairing (including QR with the real camera), the idle board, the artifact viewer, chat, approvals and app switching.

Checklist

  • Branched from main (or continuing an existing PR branch)
  • One focused change; links the related issue when applicable
  • Follows AGENTS.md conventions and PR hygiene
  • Before / After filled in; UI changes include screenshots or a recording
  • Tests added/updated for user-visible behavior where it makes sense
  • Relevant CI checks pass for the area touched (go, frontend, etc.)

@github-actions

github-actions Bot commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

🏆 Review leaderboard

Oct 31, 2026–Nov 7, 2026 · UTC

Rank Reviewer PRs reviewed Review rounds PR comments
🥇 @ronishrohan @ronishrohan 59 87 13
🥈 @Rishet11 @Rishet11 26 49 19
🥉 @Vaibhaav-Tiwari @Vaibhaav-Tiwari 26 35 4
4 @nikhilachale @nikhilachale 13 64 5
5 @somewherelostt @somewherelostt 11 48 1
6 @illegalcall @illegalcall 10 20 4
7 @Prasad-D-Ware @Prasad-D-Ware 10 14 0
8 @Meraj-08 @Meraj-08 7 12 0
9 @Pritom14 @Pritom14 6 7 4
10 @Annieeeee11 @Annieeeee11 5 7 2

Ranked by distinct external PRs reviewed, then review rounds, then PR comments. Self-activity and bot activity are excluded.

Show 8 more reviewers
Rank Reviewer PRs reviewed Review rounds PR comments
11 @neversettle17-101 @neversettle17-101 5 6 3
12 @ApexYash11 @ApexYash11 4 13 2
13 @mohakchakraborty2004 @mohakchakraborty2004 4 5 2
14 @codebanditssss @codebanditssss 4 4 0
15 @harshitsinghbhandari @harshitsinghbhandari 2 3 0
16 @Vansh-Singhal @Vansh-Singhal 1 3 0
17 @wesleymatosdev @wesleymatosdev 1 2 1
18 @AgentWrapper @AgentWrapper 1 1 0

@ronishrohan
ronishrohan merged commit dab2eef into main Nov 7, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants